Thanks @hannesa2 , this is a good step after merging the modularization into master, I will put it inside new architecture epic

Why not now ?
I at least see no reason to postpone it

Why not now ?

Many changes have taken place during modularization, a bunch of new files have been created, old files have been removed. If we move forward the lint check before merging modularization we could have lint suggestions that are already solved.

I'd rather include lint check and start fixing the suggestions after the huge structural change of modularization. Besides, the modularization merge into master should not take long, the last PR is ready to code review => #2728

Interesting point of view.
To resume it: This PR has no blocking lint issues, I solved all blockers in this PR !

Knowing this, there are two ways:
A: merging this PR now, and you have to solve your hypothetical lint by yourself
B: merging this PR after your merge, and I've to solve your hypothetical lint by me in this PR

To be honest, that's cheeky

A: merging this PR now, and you have to solve your hypothetical lint by yourself
B: merging this PR after your merge, and I've to solve your hypothetical lint by me in this PR

To be honest, that's cheeky

1. Please stop using sarcasm and these your , I've accusations, are disrespectful and being respectful is one of the main points of our community code of conduct. Besides, using "cheeky" is out of place here, specially when some of your PRs have not been finished by yourself - applying requested changes or fixing reported bugs and that's what every contributor or developer we have had has always done with no complains - and we have helped you to move them forward, last example => Better logging gui #2725.

2. No one said you have to solve the lint suggestions in this PR after merging modularization, sorry if I did not explain myself properly. My idea was taking advantage of this PR and applying the lint suggestions of modularization here by ourselves, in the different modules and so on... addressing all the work related to the lint here and not splitting it up into different issues.

To sum up, I do not want to delay more the modularization merge into master and merging this PR before will block it, since the modularization build will fail because of lint errors (see below) and no modularization merge will be possible till fixing the lint errors.

Therefore, just after merging the modularization into master, we will enable the lint check via this PR y start to work on it (I will do it, no problem).

Will be continued on #2750